Technology Strategy Patterns: Analyzing and Communicating Architectural Decisions
- Downloads：7859
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-04-14 13:54:31
- Update Date：2025-09-06
- Status：finish
- Author：Eben Hewitt
- ISBN：1492040878
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
Software architects are often called upon to create an organization's technology strategy。 But what constitutes a "good" technology strategy？ And what tools and patterns can you use to create one that's meaningful， impactful， executable， and operational？ This book explains what the world's top strategy firms can teach you about the intersection of strategic analysis and communication to deliver critical architectural decisions。
Author Eben Hewitt， Chief Architect and VP of Product Development at Sabre， outlines a framework， process， and set of 30 patterns that will help you create a powerful technology strategy for your organization。 You'll learn what strategy is and explore the accepted tools and patterns for creating one， including SWOT， Porter's Five Forces， PESTEL， Futures Funnels， and radars。
By the end of the book， you'll be able to apply these tested patterns to represent your technology strategy in a way that will help you succeed。
Author Eben Hewitt， Chief Architect and VP of Product Development at Sabre， outlines a framework， process， and set of 30 patterns that will help you create a powerful technology strategy for your organization。 You'll learn what strategy is and explore the accepted tools and patterns for creating one， including SWOT， Porter's Five Forces， PESTEL， Futures Funnels， and radars。
By the end of the book， you'll be able to apply these tested patterns to represent your technology strategy in a way that will help you succeed。
Reviews
Chester Brian
，
Full of meaningful insights and practical advice。 If you're a technology leader or just interested in strategy you shouldn't miss out on this book。 Full of meaningful insights and practical advice。 If you're a technology leader or just interested in strategy you shouldn't miss out on this book。 。。。more
Piotr Tomaszewski
，
I like framework-style books， and Technology Strategy Patterns fits into this category nicely。The book is dedicated to the particular area of strategy development， so don’t get confused by the title - it is not about technology。 Instead， you will find a set of helpful patterns that may foster your strategy development efforts， and you will be guided on how to use this knowledge。 If you are developing an IT strategy， this book will give you all you need to succeed。The target audience is Architect I like framework-style books， and Technology Strategy Patterns fits into this category nicely。The book is dedicated to the particular area of strategy development， so don’t get confused by the title - it is not about technology。 Instead， you will find a set of helpful patterns that may foster your strategy development efforts， and you will be guided on how to use this knowledge。 If you are developing an IT strategy， this book will give you all you need to succeed。The target audience is Architects， and I think CxOs。 They will have the most significant value in reading Technology Strategy Patterns。 The best parts for me are communication and mental models， analysis and decision making。For me， the book was handy - healthy four stars。 。。。more
Oneeb
，
Great emphasis on important techniques and patterns critical to a technology strategy engagements。 While some of the frameworks such as Porter five forces， BCG growth matrix were generic， others such as the ones below were more practical and are currently used today:1） Capability Mapping （People， process， technology etc）2） Enterprise architecture （business， data， information， application）3） Vision and principles4） Operating model design5） Business process and value stream mapping （lean 6 sigma）6 Great emphasis on important techniques and patterns critical to a technology strategy engagements。 While some of the frameworks such as Porter five forces， BCG growth matrix were generic， others such as the ones below were more practical and are currently used today:1） Capability Mapping （People， process， technology etc）2） Enterprise architecture （business， data， information， application）3） Vision and principles4） Operating model design5） Business process and value stream mapping （lean 6 sigma）6） Target State design7） Applications Portfolio Mapping according to asset classes8。 Culture and Change Management， Training and support9。 Use case design， initiatives and implementation roadmapGreat book overall。 。。。more
Hossam
，
I believe that every technologist， architect and strategist will relate or appreciate to a big extent the practicality of the techniques and structure Eben brought to life in this brilliant work。 It is one thing to theorize about strategy and architecture as in many of the conventional literature， versus getting things put forward pragmatically from the practitioner's perspective， and that what this book is about。Ebin dedicates a great deal of detailed chapters to explain core strategy tools in I believe that every technologist， architect and strategist will relate or appreciate to a big extent the practicality of the techniques and structure Eben brought to life in this brilliant work。 It is one thing to theorize about strategy and architecture as in many of the conventional literature， versus getting things put forward pragmatically from the practitioner's perspective， and that what this book is about。Ebin dedicates a great deal of detailed chapters to explain core strategy tools in action and how and when to use it in a context that is technology and architecture driven。 Examples， MECE， PESTEL， Scenario Planning， Future Funnel， Backcasting， Porter's Five Forces， Value Chain， Growth-Share Matrix， Core/Innovation Map， Application Portfolio Management， and much more。 It also goes beyond the strategy formulation and pays more focus and attention to how to present， structure and communicate the strategy in concise and impactful ways。I enjoyed reading through the chapters and found it addressing the core challenges faced in every day corporates。 The book provides a clear guide and pattern-based approach to technology strategy formulation through careful examination for the outer and inner circles that influence the organization including macro-trends， industry focus and even department-wide dynamics。 I would highly recommend for anyone in information technology who wants to do more strategic， relevant， meaningful work for their organizations。 。。。more
Y。 Mithat C
，
Firstly， this is a hands-on book。It is a great book shows the way from strategy to execution in a "very" practical approach。 However， it does not forget to link practicals to philosophy and fundamental logic。My takeaways; I've been using similar methods and tools for a very long time。 This book shows some new ones and news ways to use the old ones。 There are some missing point。 For example; it'd be better to have template for SBM。 Firstly， this is a hands-on book。It is a great book shows the way from strategy to execution in a "very" practical approach。 However， it does not forget to link practicals to philosophy and fundamental logic。My takeaways; I've been using similar methods and tools for a very long time。 This book shows some new ones and news ways to use the old ones。 There are some missing point。 For example; it'd be better to have template for SBM。 。。。more
George Hipp
，
There is a large amount of information crammed into this book， in a good way！ Starting with the roles （Architect and Strategy）， through analyzing the environment at many levels to create a strategy and then communicating / selling the strategy to "leadership" and the rest of the organization。 There is a ton of detail and how-to's， suggestions and examples。 I would not recommend this book to a junior developer who would like to suggest a new framework on a project， but a mid-career architect / se There is a large amount of information crammed into this book， in a good way！ Starting with the roles （Architect and Strategy）， through analyzing the environment at many levels to create a strategy and then communicating / selling the strategy to "leadership" and the rest of the organization。 There is a ton of detail and how-to's， suggestions and examples。 I would not recommend this book to a junior developer who would like to suggest a new framework on a project， but a mid-career architect / senior developer who is looking to make a larger contribution to strategic thought in their organization could find some good value here。 It is meant to be technical and could make a good reference when looking for ideas around how to create or communicate a technology strategy。I did enjoy the book and it will be staying on my shelf for reference！ 。。。more
Fausto De
，
Very pragmatic lessons that an Architect can apply to talk with business people and executives
Railgun
，
Like the author said， this is a book for the wannabe CTOs。 The content is about helping us form and present a technology strategy to the audience - the CEO and the board。
Rafal Gruszczynski
，
A collection of tools and techniquesPretty basic collection of tools and techniques related to software and organisation building。 In fact trying to some extent to map one onto the other。 Interesting and can help organising things a bit better。 Of limited value。 You'd better invest your time elsewhere。 A collection of tools and techniquesPretty basic collection of tools and techniques related to software and organisation building。 In fact trying to some extent to map one onto the other。 Interesting and can help organising things a bit better。 Of limited value。 You'd better invest your time elsewhere。 。。。more
Denis Romanovsky
，
Technology strategist/enterprise architect explains how to use strategic thinking and strategic analysis tools。 Does this really well and easy to comprehend。 Good for any technology leaders。
Ryan
，
Good material but a bit of a slog reading cover-to-coverThe beginning of this book has some wonderful insights and perspectives on software architecture and the role in business and there really are some great patterns outlined that I’ll probably refer back to time to time， but it was quite a slog reading this cover-to-cover。 I ended up skimming after I got to the 10th pattern or so。 It is also aimed more at executive-level architects at more traditional businesses， so was a bit dry and stodgy i Good material but a bit of a slog reading cover-to-coverThe beginning of this book has some wonderful insights and perspectives on software architecture and the role in business and there really are some great patterns outlined that I’ll probably refer back to time to time， but it was quite a slog reading this cover-to-cover。 I ended up skimming after I got to the 10th pattern or so。 It is also aimed more at executive-level architects at more traditional businesses， so was a bit dry and stodgy in its approach。 With that said， I’d recommend this to anyone who is involved in software architecture or any kind of technical business strategy， as I think it can really help level up communicating and connecting technology to the larger business。 。。。more
Kiran K
，
Along with concepts real life examples are well explained。 This is one of my first books which helped me articulate non functional requirements to Senior leadership。
Harlan
，
I really wanted this to be a different book， and was pretty disappointed。 There are some good patterns in here， particularly towards the end， and I will come back to them; but the first half of the book was primarily long， chatty descriptions of processes that are so high-level to be incomprehensible， with asides on philosophy that are irrelevant。 Despite the back-cover blurb talking about "examples"， the examples he gives are disjoint and usually just painfully-shrunken screenshots， rather than I really wanted this to be a different book， and was pretty disappointed。 There are some good patterns in here， particularly towards the end， and I will come back to them; but the first half of the book was primarily long， chatty descriptions of processes that are so high-level to be incomprehensible， with asides on philosophy that are irrelevant。 Despite the back-cover blurb talking about "examples"， the examples he gives are disjoint and usually just painfully-shrunken screenshots， rather than what was needed， which was walk-throughs of the thought-processes that would let an MBA-free reader actually apply most of the strategy patterns effectively。 。。。more
Patrick
，
An opinionated overview of the building blocks necessary to create an architecture strategy， this is a great guide for technologists who need to learn to begin working with the executive ranks。 The book is a collection of business strategy exercises， facilitation techniques， and presentation advice。 Recommended。
Gerhard Kessell-haak
，
A very good overview of useful techniques and patterns to assist when putting together a technology focussed strategy。 I didn't personally find much that was new， but it is a nice compendium that you can leaf through when compiling your thoughts and figuring out how best to support and communicate your strategy。 A very good overview of useful techniques and patterns to assist when putting together a technology focussed strategy。 I didn't personally find much that was new， but it is a nice compendium that you can leaf through when compiling your thoughts and figuring out how best to support and communicate your strategy。 。。。more
Simon Gianoutsos
，
This book does contain a bunch of good patterns and guidance of what to include in a Technology Strategy and a great starting point for what to include in an Architecture Definition。 As a shopping list of things to consider putting in a strategy it is good， but reading through each of them was a bit dry。
Sebastian Gebski
，
An ultra-specific book for certain category of people - "high-value consultants"， enterprise architecture strategists， technical executives very far from the actual technology - I've been there， so I can honestly say: this book is useful for them。Everyone else？ Move along。To keep the long story short， this is a collection of simple techniques to communicate enterprise architecture in the simplest， most clear & effective way。 It is NOT about technology， not about people or processes - it's all ab An ultra-specific book for certain category of people - "high-value consultants"， enterprise architecture strategists， technical executives very far from the actual technology - I've been there， so I can honestly say: this book is useful for them。Everyone else？ Move along。To keep the long story short， this is a collection of simple techniques to communicate enterprise architecture in the simplest， most clear & effective way。 It is NOT about technology， not about people or processes - it's all about strategy， vision & making （/influencing） important decisions about strategy or technology vision。Is there anything in particular I really liked in this book？ Yes。 It starts with the very basics （literally 101） of presenting clear & ultra-concise information and 。。。 some concepts presented here （that I use for 20 years 。。。） have been explicitly named （like MECE） & emphasised - that's what I really needed: sometimes you have a junior team member & you feel that the message （or output of analysis （s）he presents to you is chaotic） - sometimes I couldn't frame what this chaos was about， now I have framed concepts that will help me feedback such a person。 。。。more
Thomas
，
This book is borderline between four and five stars for me。 We'll see as I'm able to really start applying these patterns whether it proves to be as useful as it seems。 One word of warning， I won't be surprised to see some less than positive reviews of this book from readers who come to it looking for something very different。 Just be warned， if you are not looking for advice and patterns for approaching the *business* side of technical strategy， don't bother with this book。 If you are looking f This book is borderline between four and five stars for me。 We'll see as I'm able to really start applying these patterns whether it proves to be as useful as it seems。 One word of warning， I won't be surprised to see some less than positive reviews of this book from readers who come to it looking for something very different。 Just be warned， if you are not looking for advice and patterns for approaching the *business* side of technical strategy， don't bother with this book。 If you are looking for that， this book is full of great resources。 If nothing else， it taught me about quite a few ideas and additional areas that I needed to investigate more。 My favorite non-fiction books are usually the ones that lead me to even more sources to read and learn from and this book definitely met that mark。 。。。more
Shane Sexton
，
An excellent set of conceptual tools for making strategic decisions。 I suspect I will be returning to this book frequently in the future。
Daniel Rezny
，
Good set of pattern how to build an architecture from the beginning till the real strategical architecture。 Very important is communication！I will， for sure try some of these techniques
Jevgenij
，
I admire the attempt to make the work of architects and analysts more structured， but the reality is that all those "patterns" are just a lot of water invented by business people。 In reality there is only one pattern: logical thinking， experience and research。 I admire the attempt to make the work of architects and analysts more structured， but the reality is that all those "patterns" are just a lot of water invented by business people。 In reality there is only one pattern: logical thinking， experience and research。 。。。more
Thanonchai
，